Add Files API support for image attachments #1462
Open
+2,031
−200
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
https://platform.openai.com/docs/api-reference/files should be similar in concept to the anthropic process implemented |
rumpl
reviewed
Jan 21, 2026
| URL: part.ImageURL.URL, | ||
| })) | ||
| // Use the image converter which handles file refs, data URLs, and HTTP URLs | ||
| if imgBlock := convertImagePart(context.Background(), nil, part.ImageURL); imgBlock != nil { |
Member
There was a problem hiding this comment.
We should use a real context here so that we can cancel the operation
Signed-off-by: Jean-Laurent de Morlhon <jeanlaurent@morlhon.net>
jeanlaurent
force-pushed
the
attach-fileid
branch
from
e1fb4a4 to
db0ff8b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Files API support for image attachments
Images attached via /attach now use provider-specific Files APIs instead of
embedding base64 data in every message.
Changes:
• Store local file paths in messages instead of immediate base64 conversion
• Anthropic: Upload via Files API (beta), reference by file_id , with caching to
avoid re-uploads
• Gemini: Upload via Files API, reference by URI, with caching
• OpenAI/Bedrock: Convert to base64 at send time (no Files API for chat vision)
Benefits:
• Significantly reduces token usage for Anthropic (file IDs vs ~3000+ tokens per
image)
• Fixes "prompt too long" errors when attaching large images
• Each provider handles images optimally for its API